Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e29580d0f0a157161569307d1d3e40108e0c1fcea76c7849862c942fef1d29d

Tx prefix hash: a70956a050665b1c403a1a1ad521f1afa7e07ec5ebbbd62ebe0f1c34ad3343df
Tx public key: 2e29adc59c79be22455b6cad6d7d4242a55816d7eae6bf55e243afdc73719d09
Timestamp: 1713180987 Timestamp [UCT]: 2024-04-15 11:36:27 Age [y:d:h:m:s]: 01:004:00:47:56
Block: 1001014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263834 RingCT/type: yes/0
Extra: 012e29adc59c79be22455b6cad6d7d4242a55816d7eae6bf55e243afdc73719d090211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dc820e9b8daea719b5b571169446da74ef2ff1496ac9069f1cf613dd1968801 0.600000000000 1461516 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": 1001024, "vin": [ { "gen": { "height": 1001014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dc820e9b8daea719b5b571169446da74ef2ff1496ac9069f1cf613dd1968801" } } ], "extra": [ 1, 46, 41, 173, 197, 156, 121, 190, 34, 69, 91, 108, 173, 109, 125, 66, 66, 165, 88, 22, 215, 234, 230, 191, 85, 226, 67, 175, 220, 115, 113, 157, 9, 2, 17, 0, 0, 0, 2, 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