Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 611e089924bed2ff7bdaf371d3c4e7dd9f76be65306c0cb253e73d88e1481278

Tx prefix hash: e1c5186512a39362c6bb9d9d9a6e1e471566dfb682f1511a602d7a1520cccad1
Tx public key: 937ea67c656e080e720a7dcd17c120bffc1168fe459ce5b2c122a8e5619e979d
Timestamp: 1723868136 Timestamp [UCT]: 2024-08-17 04:15:36 Age [y:d:h:m:s]: 00:145:22:43:55
Block: 1089630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104396 RingCT/type: yes/0
Extra: 01937ea67c656e080e720a7dcd17c120bffc1168fe459ce5b2c122a8e5619e979d02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d379c35bc3763770d8eba7fde0cb5acc1efbda1de6386e31f11b271768b8b8a 0.600000000000 1564253 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": 1089640, "vin": [ { "gen": { "height": 1089630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d379c35bc3763770d8eba7fde0cb5acc1efbda1de6386e31f11b271768b8b8a" } } ], "extra": [ 1, 147, 126, 166, 124, 101, 110, 8, 14, 114, 10, 125, 205, 23, 193, 32, 191, 252, 17, 104, 254, 69, 156, 229, 178, 193, 34, 168, 229, 97, 158, 151, 157, 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