Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1021d69d75d2c7d33d3546c9874b145a4d43230c088cb2daa5d98cdf3a224ed

Tx prefix hash: 656ee45f98e9fd9a863b922c875c19d70afd15e6826f5380375688a850efca7a
Tx public key: 505f292b401a5b2e643c5c5a5136f1038318ac5a17ea0c68b9f3570eec53147c
Timestamp: 1728908627 Timestamp [UCT]: 2024-10-14 12:23:47 Age [y:d:h:m:s]: 00:101:10:11:23
Block: 1131414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72448 RingCT/type: yes/0
Extra: 01505f292b401a5b2e643c5c5a5136f1038318ac5a17ea0c68b9f3570eec53147c021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79c81ac64f88eeb009320fcf48f915b7ea80aaa5d1bb6ad7212e569b5e60a4ff 0.600000000000 1614313 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": 1131424, "vin": [ { "gen": { "height": 1131414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79c81ac64f88eeb009320fcf48f915b7ea80aaa5d1bb6ad7212e569b5e60a4ff" } } ], "extra": [ 1, 80, 95, 41, 43, 64, 26, 91, 46, 100, 60, 92, 90, 81, 54, 241, 3, 131, 24, 172, 90, 23, 234, 12, 104, 185, 243, 87, 14, 236, 83, 20, 124, 2, 17, 0, 0, 0, 4, 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