Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c9f83afa1e81447b693ddfbb2c85a497a4abed73f11a610eac2debc672c2a73

Tx prefix hash: cf9b504f73562a63e078bea21377d1c514be9d3c35597ee2630eaac3f0c97fd5
Tx public key: 047cefdb39625f96281f5c0ce8351e6e262d60bae4274462093416977b3ae81a
Timestamp: 1737430524 Timestamp [UCT]: 2025-01-21 03:35:24 Age [y:d:h:m:s]: 00:055:09:07:48
Block: 1201869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39408 RingCT/type: yes/0
Extra: 01047cefdb39625f96281f5c0ce8351e6e262d60bae4274462093416977b3ae81a0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a60ca1459c35a1d559bc3408c9ecbd349b3db440eda3c85636c6f95e9952c298 0.600000000000 1688526 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": 1201879, "vin": [ { "gen": { "height": 1201869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a60ca1459c35a1d559bc3408c9ecbd349b3db440eda3c85636c6f95e9952c298" } } ], "extra": [ 1, 4, 124, 239, 219, 57, 98, 95, 150, 40, 31, 92, 12, 232, 53, 30, 110, 38, 45, 96, 186, 228, 39, 68, 98, 9, 52, 22, 151, 123, 58, 232, 26, 2, 17, 0, 0, 0, 1, 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