Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7292e12a4f46e90d4a89d68bbeb51c2ba76afa1a6a51db5c14b1a70101e337d6

Tx prefix hash: 55197fb877e6c1b51e9eb1c37916d49b8788d23c2bea2d1dfbb5c48fe239abaf
Tx public key: 20ad7bc5360d984967a2e38d9af7442d4c15a1bc41e18d9ff33d925e676e87f3
Timestamp: 1709507617 Timestamp [UCT]: 2024-03-03 23:13:37 Age [y:d:h:m:s]: 00:266:05:28:43
Block: 970571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190590 RingCT/type: yes/0
Extra: 0120ad7bc5360d984967a2e38d9af7442d4c15a1bc41e18d9ff33d925e676e87f30211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b19c236623361d83d6d14d884179f9626c190660034cb62b66b3580365058509 0.600000000000 1430430 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": 970581, "vin": [ { "gen": { "height": 970571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b19c236623361d83d6d14d884179f9626c190660034cb62b66b3580365058509" } } ], "extra": [ 1, 32, 173, 123, 197, 54, 13, 152, 73, 103, 162, 227, 141, 154, 247, 68, 45, 76, 21, 161, 188, 65, 225, 141, 159, 243, 61, 146, 94, 103, 110, 135, 243, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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