Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a35bdf3efe3bdf3bc43005b1606bfdc5c15c4aa2461cdf2b280b4a2413b274d0

Tx prefix hash: c2d33ab1951fae2ae32f6029bff8fb2c72e8b73b0e556ba7c2dd1f87e8ea917c
Tx public key: 8c2a1918a3d5059c2db41852b92885bd17f25914a9c297f9d34fff6fb2107b4f
Timestamp: 1724125731 Timestamp [UCT]: 2024-08-20 03:48:51 Age [y:d:h:m:s]: 01:132:10:09:36
Block: 1091763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353158 RingCT/type: yes/0
Extra: 018c2a1918a3d5059c2db41852b92885bd17f25914a9c297f9d34fff6fb2107b4f02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef0744c892225659bc341ea1b59ad18742427910e2e373071530ee0e893f30e4 0.600000000000 1566396 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": 1091773, "vin": [ { "gen": { "height": 1091763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef0744c892225659bc341ea1b59ad18742427910e2e373071530ee0e893f30e4" } } ], "extra": [ 1, 140, 42, 25, 24, 163, 213, 5, 156, 45, 180, 24, 82, 185, 40, 133, 189, 23, 242, 89, 20, 169, 194, 151, 249, 211, 79, 255, 111, 178, 16, 123, 79, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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