Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30390322d7b5cf2b6ff28042b698717a0c41bac8155fa781d0bef9d49046b3b1

Tx prefix hash: ba42aced7d211b0b4792643948deea4f36bdd9f1ff0de3975b42cdd50392e042
Tx public key: fe344d04f5ec2e20a422a702be1c67383b7aba59f432c2d8552295e7a716bcfa
Timestamp: 1738171052 Timestamp [UCT]: 2025-01-29 17:17:32 Age [y:d:h:m:s]: 00:296:08:45:55
Block: 1207788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209562 RingCT/type: yes/0
Extra: 01fe344d04f5ec2e20a422a702be1c67383b7aba59f432c2d8552295e7a716bcfa021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ca24980b79ea985b156dbf6d4a44e1919dfe0d22a339829d6a45bc0a7448685 0.600000000000 1694513 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": 1207798, "vin": [ { "gen": { "height": 1207788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ca24980b79ea985b156dbf6d4a44e1919dfe0d22a339829d6a45bc0a7448685" } } ], "extra": [ 1, 254, 52, 77, 4, 245, 236, 46, 32, 164, 34, 167, 2, 190, 28, 103, 56, 59, 122, 186, 89, 244, 50, 194, 216, 85, 34, 149, 231, 167, 22, 188, 250, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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