Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81d4d658fc8e52b8f35a3bb00263b324e180e08b5903250c57d3e4230efb8a28

Tx prefix hash: d2ad82ae0134cb8ad77107f6bbf86420d945769fadadc6341543e50456a1812c
Tx public key: 8a0d5204cf9aa2d3d22af0fa683b130c453322fbca3289040cd3a0a3a45d6f59
Timestamp: 1736183984 Timestamp [UCT]: 2025-01-06 17:19:44 Age [y:d:h:m:s]: 00:317:20:17:48
Block: 1191601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224664 RingCT/type: yes/0
Extra: 018a0d5204cf9aa2d3d22af0fa683b130c453322fbca3289040cd3a0a3a45d6f590211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 766619b571b75c43a1a98f472a7b917501be58ddaabaa5f69f3a95e7aeb20543 0.600000000000 1678140 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": 1191611, "vin": [ { "gen": { "height": 1191601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "766619b571b75c43a1a98f472a7b917501be58ddaabaa5f69f3a95e7aeb20543" } } ], "extra": [ 1, 138, 13, 82, 4, 207, 154, 162, 211, 210, 42, 240, 250, 104, 59, 19, 12, 69, 51, 34, 251, 202, 50, 137, 4, 12, 211, 160, 163, 164, 93, 111, 89, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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