Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 019f5ed6fd144a90573146f1825cdcde127cae6fc9411eacf8785368324fe746

Tx prefix hash: e98e946ee837a11c8d2f8e60ffb72bf32ca2f29e353d9c4dfa5de783eeb896a5
Tx public key: a12604f65eadb523e63e8ab315c6c8a9d2fdcd22af0801afb2a0cd75184e333a
Timestamp: 1649526126 Timestamp [UCT]: 2022-04-09 17:42:06 Age [y:d:h:m:s]: 03:016:05:33:07
Block: 476695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 792064 RingCT/type: yes/0
Extra: 01a12604f65eadb523e63e8ab315c6c8a9d2fdcd22af0801afb2a0cd75184e333a021100000001bf7ee4e7000000000000000000

1 output(s) for total of 16.162622114000 dcy

stealth address amount amount idx
00: b25fef1f0c59ba57ee7a81dca4a34ecd6e1df90c2567ca1933376b082c74e207 16.162622114000 897228 of 0

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": 476705, "vin": [ { "gen": { "height": 476695 } } ], "vout": [ { "amount": 16162622114, "target": { "key": "b25fef1f0c59ba57ee7a81dca4a34ecd6e1df90c2567ca1933376b082c74e207" } } ], "extra": [ 1, 161, 38, 4, 246, 94, 173, 181, 35, 230, 62, 138, 179, 21, 198, 200, 169, 210, 253, 205, 34, 175, 8, 1, 175, 178, 160, 205, 117, 24, 78, 51, 58, 2, 17, 0, 0, 0, 1, 191, 126, 228, 231, 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