Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8346e386e240819b41284926acbcfb48a0005b26a07b4e56373ded32d37bfe5c

Tx prefix hash: 8f2cc0364df0042744dcd5d0d02f738e1d59242f48cee81cbb6ff0daf15f4211
Tx public key: aaf997e5d0f92ce518687ee7aef2242b1bee3d9070fa25c0f33fcfdb8ed72b43
Timestamp: 1704547990 Timestamp [UCT]: 2024-01-06 13:33:10 Age [y:d:h:m:s]: 01:130:22:50:11
Block: 929429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354734 RingCT/type: yes/0
Extra: 01aaf997e5d0f92ce518687ee7aef2242b1bee3d9070fa25c0f33fcfdb8ed72b430211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9970cf9c43ef9786f4a693620ffb69f06a4d715644d1df73e2aa69313ef1f146 0.600000000000 1387301 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": 929439, "vin": [ { "gen": { "height": 929429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9970cf9c43ef9786f4a693620ffb69f06a4d715644d1df73e2aa69313ef1f146" } } ], "extra": [ 1, 170, 249, 151, 229, 208, 249, 44, 229, 24, 104, 126, 231, 174, 242, 36, 43, 27, 238, 61, 144, 112, 250, 37, 192, 243, 63, 207, 219, 142, 215, 43, 67, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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