Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: cb1db78485e59001411871c911df0f8f2f300e18dcbdc2219aba8b0ff22389ce

Tx prefix hash: 10c04d7d567bbd1de24dd355f0dea0683c729870b207b28d6f11451f684fc0dc
Tx public key: 1a7abfdf1c84ea5e03deda25883056b28a91bf23446d4b81d42d35becf513ea6
Timestamp: 1720962273 Timestamp [UCT]: 2024-07-14 13:04:33 Age [y:d:h:m:s]: 00:269:14:41:51
Block: 1065547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192613 RingCT/type: yes/0
Extra: 011a7abfdf1c84ea5e03deda25883056b28a91bf23446d4b81d42d35becf513ea602110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bf9d110f279f434d55978f804cdd456d968b8c41421787eb5a89e5293983c18 0.600000000000 1536094 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1065557, "vin": [ { "gen": { "height": 1065547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bf9d110f279f434d55978f804cdd456d968b8c41421787eb5a89e5293983c18" } } ], "extra": [ 1, 26, 122, 191, 223, 28, 132, 234, 94, 3, 222, 218, 37, 136, 48, 86, 178, 138, 145, 191, 35, 68, 109, 75, 129, 212, 45, 53, 190, 207, 81, 62, 166, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8