Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3451815c4bba09696a135a4191961424ef3d0f1a611976d211b2d24d597252ba

Tx prefix hash: d889b1da4c8252f0aa354eb1767237fcc8a442b24a190f962d7a2c3e0d24e635
Tx public key: 907c9d6ac5ce81235c7c150273fdd226cb28d2c40053755891d8eb87aa3943db
Timestamp: 1676338551 Timestamp [UCT]: 2023-02-14 01:35:51 Age [y:d:h:m:s]: 02:105:22:11:45
Block: 696471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 597344 RingCT/type: yes/0
Extra: 01907c9d6ac5ce81235c7c150273fdd226cb28d2c40053755891d8eb87aa3943db02110000000252542ceb000000000000000000

1 output(s) for total of 3.022055087000 dcy

stealth address amount amount idx
00: 1dd1ef94d9026e86fc4ccb2fd9f150b636f1ef0dda0b16fc1ea51b3d921d5049 3.022055087000 1139482 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": 696481, "vin": [ { "gen": { "height": 696471 } } ], "vout": [ { "amount": 3022055087, "target": { "key": "1dd1ef94d9026e86fc4ccb2fd9f150b636f1ef0dda0b16fc1ea51b3d921d5049" } } ], "extra": [ 1, 144, 124, 157, 106, 197, 206, 129, 35, 92, 124, 21, 2, 115, 253, 210, 38, 203, 40, 210, 196, 0, 83, 117, 88, 145, 216, 235, 135, 170, 57, 67, 219, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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