Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e7f31e00f12f8c1cd8a50683e3c089857c74d366577fe5652faec676033c616

Tx prefix hash: 8a3ebd9fcda9e02b3cde1f3c313d85675be4e69d3e17765f1f1d8ff7efbbd530
Tx public key: a82a697981940fada4549a8f5c220a35aa91569c7ab06c53c7032d9e09c5b34f
Timestamp: 1719237626 Timestamp [UCT]: 2024-06-24 14:00:26 Age [y:d:h:m:s]: 01:139:01:18:23
Block: 1051221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357948 RingCT/type: yes/0
Extra: 01a82a697981940fada4549a8f5c220a35aa91569c7ab06c53c7032d9e09c5b34f0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71c083e6c53afe2c495931f4bd729bf1f726717ff15168fda119fb3b28a44b0c 0.600000000000 1521528 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": 1051231, "vin": [ { "gen": { "height": 1051221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71c083e6c53afe2c495931f4bd729bf1f726717ff15168fda119fb3b28a44b0c" } } ], "extra": [ 1, 168, 42, 105, 121, 129, 148, 15, 173, 164, 84, 154, 143, 92, 34, 10, 53, 170, 145, 86, 156, 122, 176, 108, 83, 199, 3, 45, 158, 9, 197, 179, 79, 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