Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1c154e7d228845dab5343d25087e90f293dd08f6ee7de35d17c582e5f8f1795

Tx prefix hash: 4deb7ab7dd7a7e1677e9a3c922cbd957ea1924d663cc0bf00f4c4bfa3599a34f
Tx public key: 7c7afee85595aa771ee9d6a220dbfea6f08d491b4345857ed952860d9dd7102e
Timestamp: 1709975484 Timestamp [UCT]: 2024-03-09 09:11:24 Age [y:d:h:m:s]: 00:316:23:41:08
Block: 974452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226856 RingCT/type: yes/0
Extra: 017c7afee85595aa771ee9d6a220dbfea6f08d491b4345857ed952860d9dd7102e0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed3b78e91ab719f1859393af04ee68d2c3f8cb8e5550d6c5e55bd15a3311220d 0.600000000000 1434407 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": 974462, "vin": [ { "gen": { "height": 974452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed3b78e91ab719f1859393af04ee68d2c3f8cb8e5550d6c5e55bd15a3311220d" } } ], "extra": [ 1, 124, 122, 254, 232, 85, 149, 170, 119, 30, 233, 214, 162, 32, 219, 254, 166, 240, 141, 73, 27, 67, 69, 133, 126, 217, 82, 134, 13, 157, 215, 16, 46, 2, 17, 0, 0, 0, 4, 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