Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 147d473766c7a16ebfd434e902804453b639d70dcd7f81f503f725b4b6474253

Tx prefix hash: b8272862d4b60b086caf0b85cf9ce660401c85986aa974fb7495eb2058894e03
Tx public key: f0a42a096817b00ea78fa3aa4e6da1230fe9b19565900f3279ab8bc29b1c6bc8
Timestamp: 1699267212 Timestamp [UCT]: 2023-11-06 10:40:12 Age [y:d:h:m:s]: 01:229:09:25:14
Block: 885667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424981 RingCT/type: yes/0
Extra: 01f0a42a096817b00ea78fa3aa4e6da1230fe9b19565900f3279ab8bc29b1c6bc8021100000001679a8a81000000000000000000

1 output(s) for total of 0.713538770000 dcy

stealth address amount amount idx
00: f9cc54442ba6695eee52aa22aeeef4f36a4f302b6bc9ef1233b39991481377b1 0.713538770000 1341448 of 0

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": 885677, "vin": [ { "gen": { "height": 885667 } } ], "vout": [ { "amount": 713538770, "target": { "key": "f9cc54442ba6695eee52aa22aeeef4f36a4f302b6bc9ef1233b39991481377b1" } } ], "extra": [ 1, 240, 164, 42, 9, 104, 23, 176, 14, 167, 143, 163, 170, 78, 109, 161, 35, 15, 233, 177, 149, 101, 144, 15, 50, 121, 171, 139, 194, 155, 28, 107, 200, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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