Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7b0c78d87bfedc71aa3afc94e8fe5eed23bf72592e084f6060430c4b6ac458d

Tx prefix hash: e652086451a5a6d207fcbfc573a3a1be037acb9fb4189ac19f62a4fcdbfe56db
Tx public key: 4658f69bd38115928c8bba7f2bf6ba643b23eecfe3e790e26f4a897944d0f2d6
Timestamp: 1722700149 Timestamp [UCT]: 2024-08-03 15:49:09 Age [y:d:h:m:s]: 00:226:18:10:29
Block: 1079937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161970 RingCT/type: yes/0
Extra: 014658f69bd38115928c8bba7f2bf6ba643b23eecfe3e790e26f4a897944d0f2d6021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 380542f2253bce0a362884878b9d93ce60f3e05f96ba14f504d28f23796e03a7 0.600000000000 1553102 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": 1079947, "vin": [ { "gen": { "height": 1079937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "380542f2253bce0a362884878b9d93ce60f3e05f96ba14f504d28f23796e03a7" } } ], "extra": [ 1, 70, 88, 246, 155, 211, 129, 21, 146, 140, 139, 186, 127, 43, 246, 186, 100, 59, 35, 238, 207, 227, 231, 144, 226, 111, 74, 137, 121, 68, 208, 242, 214, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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