Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cbf4e0158d0bf3f8a13d5b8c14cf01dd249f95f1963b6e41dc68c38d51934d5

Tx prefix hash: 36401a509de0202ea3112450f04abacc86f0fd825ef2c99bafc77ee3aa4f2d7a
Tx public key: cff1557b6007e5cd7093507bc78d449899ca41e4d13eb50d251127b5572beeba
Timestamp: 1694265105 Timestamp [UCT]: 2023-09-09 13:11:45 Age [y:d:h:m:s]: 01:168:03:58:05
Block: 844383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381252 RingCT/type: yes/0
Extra: 01cff1557b6007e5cd7093507bc78d449899ca41e4d13eb50d251127b5572beeba02110000001033af99f4000000000000000000

1 output(s) for total of 0.977706868000 dcy

stealth address amount amount idx
00: 4d72d8d74865a0a315138dd955ae90dc7c1b7bd64b17917c36a5082b7a20e8d8 0.977706868000 1297687 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": 844393, "vin": [ { "gen": { "height": 844383 } } ], "vout": [ { "amount": 977706868, "target": { "key": "4d72d8d74865a0a315138dd955ae90dc7c1b7bd64b17917c36a5082b7a20e8d8" } } ], "extra": [ 1, 207, 241, 85, 123, 96, 7, 229, 205, 112, 147, 80, 123, 199, 141, 68, 152, 153, 202, 65, 228, 209, 62, 181, 13, 37, 17, 39, 181, 87, 43, 238, 186, 2, 17, 0, 0, 0, 16, 51, 175, 153, 244, 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