Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 614bd469aefb0b0bc856b8ba051b0f97bf06e816cd3a31e18e332352012e6ad8

Tx prefix hash: ed3541674209d6ce907fbd744f27a80eb41d57b8b7aa5d398fa3b6843693a64b
Tx public key: 66f82ba1e09444ffd4d7ae7c6c833b88fedc9335888d7970dc872e4341b5f8c3
Timestamp: 1739248598 Timestamp [UCT]: 2025-02-11 04:36:38 Age [y:d:h:m:s]: 00:324:15:34:58
Block: 1216701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229844 RingCT/type: yes/0
Extra: 0166f82ba1e09444ffd4d7ae7c6c833b88fedc9335888d7970dc872e4341b5f8c3021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41e551f0bd8885848711cd364181677c10d5cc87a2796864b05c8db7918bbb9a 0.600000000000 1703508 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": 1216711, "vin": [ { "gen": { "height": 1216701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41e551f0bd8885848711cd364181677c10d5cc87a2796864b05c8db7918bbb9a" } } ], "extra": [ 1, 102, 248, 43, 161, 224, 148, 68, 255, 212, 215, 174, 124, 108, 131, 59, 136, 254, 220, 147, 53, 136, 141, 121, 112, 220, 135, 46, 67, 65, 181, 248, 195, 2, 17, 0, 0, 0, 4, 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