Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e937cc0c8fd01a38a292612162d907f6686b7c856fec04412819da776d0234b3

Tx prefix hash: 771de521a4606274d1715d4ecb2b250915e9f0d1d940bfa39613c46faf17bacd
Tx public key: 293527aac60ec00d560c9f53d0090505b77d561b4b4b41b28b9c3aa11ef8db8b
Timestamp: 1736072742 Timestamp [UCT]: 2025-01-05 10:25:42 Age [y:d:h:m:s]: 00:163:11:20:54
Block: 1190682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116528 RingCT/type: yes/0
Extra: 01293527aac60ec00d560c9f53d0090505b77d561b4b4b41b28b9c3aa11ef8db8b0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6299d4124b81f627525016e0db52f51daf4ac047570c0d2d4e1eb2109d472ce9 0.600000000000 1677199 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": 1190692, "vin": [ { "gen": { "height": 1190682 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6299d4124b81f627525016e0db52f51daf4ac047570c0d2d4e1eb2109d472ce9" } } ], "extra": [ 1, 41, 53, 39, 170, 198, 14, 192, 13, 86, 12, 159, 83, 208, 9, 5, 5, 183, 125, 86, 27, 75, 75, 65, 178, 139, 156, 58, 161, 30, 248, 219, 139, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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