Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e8960029daccd1d501f0452f0818eb7c8d3870f7a0656f6da7117492c571491

Tx prefix hash: e17ea989dd401602d996256e5348363f62ac75a4ce100e5b6d4687688cf19523
Tx public key: 519bcd02a8f8ae43c0924cd6a75d06b2e581b589460bcdfd7347e26759fb22a9
Timestamp: 1733698241 Timestamp [UCT]: 2024-12-08 22:50:41 Age [y:d:h:m:s]: 00:130:09:04:07
Block: 1171037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92968 RingCT/type: yes/0
Extra: 01519bcd02a8f8ae43c0924cd6a75d06b2e581b589460bcdfd7347e26759fb22a902110000000401491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11b66e01fec4bd5004cb7d4430eff6c4fa4c8c4cbfba666acd9a63ebf5e09efb 0.600000000000 1656772 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": 1171047, "vin": [ { "gen": { "height": 1171037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11b66e01fec4bd5004cb7d4430eff6c4fa4c8c4cbfba666acd9a63ebf5e09efb" } } ], "extra": [ 1, 81, 155, 205, 2, 168, 248, 174, 67, 192, 146, 76, 214, 167, 93, 6, 178, 229, 129, 181, 137, 70, 11, 205, 253, 115, 71, 226, 103, 89, 251, 34, 169, 2, 17, 0, 0, 0, 4, 1, 73, 31, 136, 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