Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72e7aae0f470670de3df082beafa88d76820ddcfc16499f54d13977a8b12fd3a

Tx prefix hash: 402be2a147361023c7b05a0fd64775aad20a5e04a90ba6bf8e222c1046687cda
Tx public key: 4a58e063156168a96e998d9f7347745bc47fad4cde8adc4dba1e073b65748dfa
Timestamp: 1687477460 Timestamp [UCT]: 2023-06-22 23:44:20 Age [y:d:h:m:s]: 01:300:09:20:54
Block: 788177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475862 RingCT/type: yes/0
Extra: 014a58e063156168a96e998d9f7347745bc47fad4cde8adc4dba1e073b65748dfa0211000000014b8f5122000000000000000000

1 output(s) for total of 1.501213836000 dcy

stealth address amount amount idx
00: e4dfd7d79c0d9920c0e4e428f793a85c2425f17debe164c1cef8462dd08d9aa2 1.501213836000 1238276 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": 788187, "vin": [ { "gen": { "height": 788177 } } ], "vout": [ { "amount": 1501213836, "target": { "key": "e4dfd7d79c0d9920c0e4e428f793a85c2425f17debe164c1cef8462dd08d9aa2" } } ], "extra": [ 1, 74, 88, 224, 99, 21, 97, 104, 169, 110, 153, 141, 159, 115, 71, 116, 91, 196, 127, 173, 76, 222, 138, 220, 77, 186, 30, 7, 59, 101, 116, 141, 250, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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