Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bdd230c5ed2da7034b63fe0407ba08b0b72d2431dfc6f7f2bfa99a11e8ece19

Tx prefix hash: fe20526eb6b17b45377d60ae7cc003ed5ab431be41dd8a4f4e6b19c6b9ac0e08
Tx public key: 105d0129fe4526f4bca53501221e2c8047e908df058df9f75d9d9c0381ef1010
Timestamp: 1762814452 Timestamp [UCT]: 2025-11-10 22:40:52 Age [y:d:h:m:s]: 00:042:21:34:24
Block: 1409385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30712 RingCT/type: yes/0
Extra: 01105d0129fe4526f4bca53501221e2c8047e908df058df9f75d9d9c0381ef10100211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdd4d06721fb368416d21fed17ad14c2690b079338a2b60ca93902d7d347a479 0.600000000000 1897830 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": 1409395, "vin": [ { "gen": { "height": 1409385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdd4d06721fb368416d21fed17ad14c2690b079338a2b60ca93902d7d347a479" } } ], "extra": [ 1, 16, 93, 1, 41, 254, 69, 38, 244, 188, 165, 53, 1, 34, 30, 44, 128, 71, 233, 8, 223, 5, 141, 249, 247, 93, 157, 156, 3, 129, 239, 16, 16, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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