Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e66cba2817342ba7ec52860b6a0f1c514647503649dbbebd27a152f375372fe7

Tx prefix hash: 249d5ce971b2cd3b5e08d5bddb2c4f8fd701dbc7f2a3e617e5d5e08581ce62b6
Tx public key: d60c7c1c1b5894e45c941ed8e8298c19abb385e830da95ec40369c34af88ad48
Timestamp: 1716597092 Timestamp [UCT]: 2024-05-25 00:31:32 Age [y:d:h:m:s]: 00:160:00:24:28
Block: 1029352 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114537 RingCT/type: yes/0
Extra: 01d60c7c1c1b5894e45c941ed8e8298c19abb385e830da95ec40369c34af88ad480211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59e1f045cf458d984e7b22fde80eb6e246360c4819d50dc9c0f02db2ee9193f6 0.600000000000 1497419 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": 1029362, "vin": [ { "gen": { "height": 1029352 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59e1f045cf458d984e7b22fde80eb6e246360c4819d50dc9c0f02db2ee9193f6" } } ], "extra": [ 1, 214, 12, 124, 28, 27, 88, 148, 228, 92, 148, 30, 216, 232, 41, 140, 25, 171, 179, 133, 232, 48, 218, 149, 236, 64, 54, 156, 52, 175, 136, 173, 72, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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