Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27eeb31942e11bddcafe7fa5e9f2232f939009c934ca7eefd2e162244c8e92bc

Tx prefix hash: b55b21ea4dc97ad735eca602aac56e0fb6d7dec5838ad50992d417b9bcbbb5ed
Tx public key: fa43b3db54b96af75bad0a6e80477bd1efb961a1dce8d5bbf30b981f6e7a0857
Timestamp: 1763138259 Timestamp [UCT]: 2025-11-14 16:37:39 Age [y:d:h:m:s]: 00:012:17:41:38
Block: 1412062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 9126 RingCT/type: yes/0
Extra: 01fa43b3db54b96af75bad0a6e80477bd1efb961a1dce8d5bbf30b981f6e7a0857021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32470cbcd8ddc93739323a34ae5925618be21d441d63ab78dc8c0ede524e0127 0.600000000000 1900527 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": 1412072, "vin": [ { "gen": { "height": 1412062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32470cbcd8ddc93739323a34ae5925618be21d441d63ab78dc8c0ede524e0127" } } ], "extra": [ 1, 250, 67, 179, 219, 84, 185, 106, 247, 91, 173, 10, 110, 128, 71, 123, 209, 239, 185, 97, 161, 220, 232, 213, 187, 243, 11, 152, 31, 110, 122, 8, 87, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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