Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cec61123fc6dd3d1899a9d8f866ca192fefc2b19cf62e975e8f58e0e70e33980

Tx prefix hash: c77c468618dda00ebd3e45e54cf676c00992ac6057494dbd736384567eec631e
Tx public key: 93794eac65820176c6ea0613c051fef97c9e47b334807dc4325d76f9a65f33b4
Timestamp: 1725332741 Timestamp [UCT]: 2024-09-03 03:05:41 Age [y:d:h:m:s]: 00:283:07:20:11
Block: 1101767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202319 RingCT/type: yes/0
Extra: 0193794eac65820176c6ea0613c051fef97c9e47b334807dc4325d76f9a65f33b4021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbe0986a751258b6f9d2fdaccd27a942d6fd6f42f534577f8db27a8dbeaf3d3e 0.600000000000 1577942 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": 1101777, "vin": [ { "gen": { "height": 1101767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbe0986a751258b6f9d2fdaccd27a942d6fd6f42f534577f8db27a8dbeaf3d3e" } } ], "extra": [ 1, 147, 121, 78, 172, 101, 130, 1, 118, 198, 234, 6, 19, 192, 81, 254, 249, 124, 158, 71, 179, 52, 128, 125, 196, 50, 93, 118, 249, 166, 95, 51, 180, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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