Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f084bec36ef6b054ff5b289156956c69a3e17c8b47f926931a198a94d7389ec4

Tx prefix hash: 00341de11fd769b13d06c397eecf1116d9cfa5308c037d61b3a76da89d932447
Tx public key: 36a6bc99523f4551f97cc1fa178f4a5c7018e3514b0db51ef7cb92504f97c8fc
Timestamp: 1731846847 Timestamp [UCT]: 2024-11-17 12:34:07 Age [y:d:h:m:s]: 00:325:20:13:00
Block: 1155668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230378 RingCT/type: yes/0
Extra: 0136a6bc99523f4551f97cc1fa178f4a5c7018e3514b0db51ef7cb92504f97c8fc021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ced1a1c9c137d3ac015d2b6e964ff3a302b11f392d5037a772def60c965bfe93 0.600000000000 1641285 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": 1155678, "vin": [ { "gen": { "height": 1155668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ced1a1c9c137d3ac015d2b6e964ff3a302b11f392d5037a772def60c965bfe93" } } ], "extra": [ 1, 54, 166, 188, 153, 82, 63, 69, 81, 249, 124, 193, 250, 23, 143, 74, 92, 112, 24, 227, 81, 75, 13, 181, 30, 247, 203, 146, 80, 79, 151, 200, 252, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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