Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4f2f52ef3b893f7c71fd97aba2f5e8dff28de381eca66a7d996286948a72428

Tx prefix hash: b28b367c1bdd8b8d625497431789b7189783d6cbb44f9c68e390564d08e9b58d
Tx public key: 87943bf8d530ae178e042a83d209eda4b1ccb73c42b0b73c080276ae7428d466
Timestamp: 1740911286 Timestamp [UCT]: 2025-03-02 10:28:06 Age [y:d:h:m:s]: 00:264:12:56:15
Block: 1230458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186817 RingCT/type: yes/0
Extra: 0187943bf8d530ae178e042a83d209eda4b1ccb73c42b0b73c080276ae7428d466021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7eba0d40499c385f29ad8f654d9aba2c3aa96fba51df020db32f84a099742851 0.600000000000 1717357 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": 1230468, "vin": [ { "gen": { "height": 1230458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7eba0d40499c385f29ad8f654d9aba2c3aa96fba51df020db32f84a099742851" } } ], "extra": [ 1, 135, 148, 59, 248, 213, 48, 174, 23, 142, 4, 42, 131, 210, 9, 237, 164, 177, 204, 183, 60, 66, 176, 183, 60, 8, 2, 118, 174, 116, 40, 212, 102, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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