Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4de3aee74a894e0d0115f6afa9e721744bbc3fdd7dc1fbc961192254cdf90ce2

Tx prefix hash: f883c8024a977455fab410f6846206b3ba1d3b64e7bf66df9aeaae7997d66291
Tx public key: 322bae03e7a9cca45838e26d76a716a0ff8aa33cfec0c0440b265d50dc5a8cf4
Timestamp: 1694781918 Timestamp [UCT]: 2023-09-15 12:45:18 Age [y:d:h:m:s]: 01:249:17:26:03
Block: 848669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439609 RingCT/type: yes/0
Extra: 01322bae03e7a9cca45838e26d76a716a0ff8aa33cfec0c0440b265d50dc5a8cf4021100000007faf35c9c000000000000000000

1 output(s) for total of 0.946253202000 dcy

stealth address amount amount idx
00: b61b6d0e216a08460c9e36a34337d57a9a3d6143c30046387cdbbf4e323131a9 0.946253202000 1302287 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": 848679, "vin": [ { "gen": { "height": 848669 } } ], "vout": [ { "amount": 946253202, "target": { "key": "b61b6d0e216a08460c9e36a34337d57a9a3d6143c30046387cdbbf4e323131a9" } } ], "extra": [ 1, 50, 43, 174, 3, 231, 169, 204, 164, 88, 56, 226, 109, 118, 167, 22, 160, 255, 138, 163, 60, 254, 192, 192, 68, 11, 38, 93, 80, 220, 90, 140, 244, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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