Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ecdd2fa5b3d0f8d1f3ee6eb68baee7ea14bf8e96b312c228677f6381a4c9cd84

Tx prefix hash: 7a9212a7375c79f080d0465aeed50c507cf4f40e8074011cda917eb92d54d2b1
Tx public key: da1342328b7a15c9dae0ee0558f7a66d8f2369b9c1bb97fa37dace12c46f63cf
Timestamp: 1733714867 Timestamp [UCT]: 2024-12-09 03:27:47 Age [y:d:h:m:s]: 00:109:04:49:03
Block: 1171156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77831 RingCT/type: yes/0
Extra: 01da1342328b7a15c9dae0ee0558f7a66d8f2369b9c1bb97fa37dace12c46f63cf021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f475379f5a1c431c4d2acd4a137f74ade35b26778350a64cf293bd82500c7418 0.600000000000 1656893 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": 1171166, "vin": [ { "gen": { "height": 1171156 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f475379f5a1c431c4d2acd4a137f74ade35b26778350a64cf293bd82500c7418" } } ], "extra": [ 1, 218, 19, 66, 50, 139, 122, 21, 201, 218, 224, 238, 5, 88, 247, 166, 109, 143, 35, 105, 185, 193, 187, 151, 250, 55, 218, 206, 18, 196, 111, 99, 207, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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