Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3333b420ac37722072d5b0ab720690629d969655e133aec6e1a88be10a7b9c84

Tx prefix hash: 83d0a4d4cad52f429562f32a5819938cd92ac5c69e2ab9df521411663bba164e
Tx public key: 41fbdcab2927599ab6dfa164a9e13ea99d2b4b7a8f2ca85210d1fa34f3ff317e
Timestamp: 1737044261 Timestamp [UCT]: 2025-01-16 16:17:41 Age [y:d:h:m:s]: 00:068:03:54:50
Block: 1198710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48481 RingCT/type: yes/0
Extra: 0141fbdcab2927599ab6dfa164a9e13ea99d2b4b7a8f2ca85210d1fa34f3ff317e021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46097abe83147ab17c93e5eb2e13c5df83902a8d0adbf1a4f00ccd084ba5544a 0.600000000000 1685337 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": 1198720, "vin": [ { "gen": { "height": 1198710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46097abe83147ab17c93e5eb2e13c5df83902a8d0adbf1a4f00ccd084ba5544a" } } ], "extra": [ 1, 65, 251, 220, 171, 41, 39, 89, 154, 182, 223, 161, 100, 169, 225, 62, 169, 157, 43, 75, 122, 143, 44, 168, 82, 16, 209, 250, 52, 243, 255, 49, 126, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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