Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12aeeb850f74019963dbafa5218a719a87d0cbcaab0fad6b141a2551842e6280

Tx prefix hash: 7054d4a446550b04ba6dece01df457977d42c397c77f550fd9c282da5627fa2b
Tx public key: 548dc1cf9e380e311e733be8104e4ddcc0e9c6bbf9843f279c1a0a1aa75e4903
Timestamp: 1716713425 Timestamp [UCT]: 2024-05-26 08:50:25 Age [y:d:h:m:s]: 00:311:18:43:06
Block: 1030319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222811 RingCT/type: yes/0
Extra: 01548dc1cf9e380e311e733be8104e4ddcc0e9c6bbf9843f279c1a0a1aa75e49030211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2545f677d8872d1a5de04ef49310408e0555da8de7a05b79fdce6c0cc158b96 0.600000000000 1498574 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": 1030329, "vin": [ { "gen": { "height": 1030319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2545f677d8872d1a5de04ef49310408e0555da8de7a05b79fdce6c0cc158b96" } } ], "extra": [ 1, 84, 141, 193, 207, 158, 56, 14, 49, 30, 115, 59, 232, 16, 78, 77, 220, 192, 233, 198, 187, 249, 132, 63, 39, 156, 26, 10, 26, 167, 94, 73, 3, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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