Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d274dd7182792030f49869c7db099a03081cf2663381e7e0e7080b456c8bb2fc

Tx prefix hash: 87fa194a2c60ab9150253524fade7bd55f5ecc8fb9794bcbd73e59a67c74e96e
Tx public key: d4c7e81a4d5d77fd76ef9d2dad338382ff34bbdfb703d386b6d9bfa328b5e0c2
Timestamp: 1753700323 Timestamp [UCT]: 2025-07-28 10:58:43 Age [y:d:h:m:s]: 00:122:23:09:42
Block: 1335163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86736 RingCT/type: yes/0
Extra: 01d4c7e81a4d5d77fd76ef9d2dad338382ff34bbdfb703d386b6d9bfa328b5e0c2021100000002ef221485000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38cf343bdde102ca2f06526225493399271451da4b797d96f209bab9a184ddd6 0.600000000000 1822964 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": 1335173, "vin": [ { "gen": { "height": 1335163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38cf343bdde102ca2f06526225493399271451da4b797d96f209bab9a184ddd6" } } ], "extra": [ 1, 212, 199, 232, 26, 77, 93, 119, 253, 118, 239, 157, 45, 173, 51, 131, 130, 255, 52, 187, 223, 183, 3, 211, 134, 182, 217, 191, 163, 40, 181, 224, 194, 2, 17, 0, 0, 0, 2, 239, 34, 20, 133, 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