Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8411147569a8d7635412f67750798a6b9f5345a0ad87063fe20cad0f63fce5e9

Tx prefix hash: dcbbb697ebd02d9c5fe93b1530b2f0c72e5dff631f0bd57d812bcef3c00d9631
Tx public key: 40b9f5239c9fdf75cd429e90d87bdebd901eb98deef2a22ec9c5b7e0c43972f1
Timestamp: 1704402562 Timestamp [UCT]: 2024-01-04 21:09:22 Age [y:d:h:m:s]: 01:147:12:58:25
Block: 928221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366619 RingCT/type: yes/0
Extra: 0140b9f5239c9fdf75cd429e90d87bdebd901eb98deef2a22ec9c5b7e0c43972f102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 283dca879ccd22713d956e578739f89f84911d21d5a9c175fdbac2bf88630363 0.600000000000 1386079 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": 928231, "vin": [ { "gen": { "height": 928221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "283dca879ccd22713d956e578739f89f84911d21d5a9c175fdbac2bf88630363" } } ], "extra": [ 1, 64, 185, 245, 35, 156, 159, 223, 117, 205, 66, 158, 144, 216, 123, 222, 189, 144, 30, 185, 141, 238, 242, 162, 46, 201, 197, 183, 224, 196, 57, 114, 241, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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