Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0919fe0c4198f6c4254d4f478e946192a25bd1b957ed0db41cb6c5903ad7ed6e

Tx prefix hash: 770ebf6344cfa3ac3b77f613da3af35047f467ca81dea6b950826c584d5093f1
Tx public key: dc8824d478fb00fc4f6fcb20e563c38cea9a47684ac5d8755f998407cc43c396
Timestamp: 1761551357 Timestamp [UCT]: 2025-10-27 07:49:17 Age [y:d:h:m:s]: 00:073:12:56:30
Block: 1398930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52648 RingCT/type: yes/0
Extra: 01dc8824d478fb00fc4f6fcb20e563c38cea9a47684ac5d8755f998407cc43c39602110000000625a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02b60a0f1bb64f4a27176f810bea6c1a652589962c09ca728537cb4998771331 0.600000000000 1887233 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": 1398940, "vin": [ { "gen": { "height": 1398930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02b60a0f1bb64f4a27176f810bea6c1a652589962c09ca728537cb4998771331" } } ], "extra": [ 1, 220, 136, 36, 212, 120, 251, 0, 252, 79, 111, 203, 32, 229, 99, 195, 140, 234, 154, 71, 104, 74, 197, 216, 117, 95, 153, 132, 7, 204, 67, 195, 150, 2, 17, 0, 0, 0, 6, 37, 163, 90, 15, 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