Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e4fd1310dd582651135cdc2922b553b4a1220eb3a5f359867874d0b2ece7f11

Tx prefix hash: 467d6707d285830b861affbe10d23ee82d0527db43046f7b3c81a977702e921c
Tx public key: 136f6f09aa91df4839b127b2c41714c5625c02afd6ad6145661413e3555bc6db
Timestamp: 1578236424 Timestamp [UCT]: 2020-01-05 15:00:24 Age [y:d:h:m:s]: 05:050:13:53:21
Block: 39265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1186001 RingCT/type: yes/0
Extra: 01136f6f09aa91df4839b127b2c41714c5625c02afd6ad6145661413e3555bc6db021100000056ff58ae94000000000000000000

1 output(s) for total of 454.890742600000 dcy

stealth address amount amount idx
00: 41f42a3178c20c3489277b3aa1d04e55aa5320c1b67fc44e676c8383ce3e5957 454.890742600000 67572 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": 39275, "vin": [ { "gen": { "height": 39265 } } ], "vout": [ { "amount": 454890742600, "target": { "key": "41f42a3178c20c3489277b3aa1d04e55aa5320c1b67fc44e676c8383ce3e5957" } } ], "extra": [ 1, 19, 111, 111, 9, 170, 145, 223, 72, 57, 177, 39, 178, 196, 23, 20, 197, 98, 92, 2, 175, 214, 173, 97, 69, 102, 20, 19, 227, 85, 91, 198, 219, 2, 17, 0, 0, 0, 86, 255, 88, 174, 148, 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