Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 633cd2724594d93c8a8a70745b7c3249ff19434c9d4776b0d7513591f70efba1

Tx prefix hash: 118ea5f6c4f34a6e79a0b9c696fb1702ff716dcf22fa8afde3d235bf8bcd83d3
Tx public key: 5964b4605b8c56428beb99b86de07375bdfbf2f5ae8ae7a065d4d2b1004033ee
Timestamp: 1763908575 Timestamp [UCT]: 2025-11-23 14:36:15 Age [y:d:h:m:s]: 00:003:19:39:39
Block: 1418452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2736 RingCT/type: yes/0
Extra: 015964b4605b8c56428beb99b86de07375bdfbf2f5ae8ae7a065d4d2b1004033ee02110000000470609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5636a5f6ad3580b478c745f7adf37762733ec7b6148be275b5f02e9061ab6e00 0.600000000000 1906983 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": 1418462, "vin": [ { "gen": { "height": 1418452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5636a5f6ad3580b478c745f7adf37762733ec7b6148be275b5f02e9061ab6e00" } } ], "extra": [ 1, 89, 100, 180, 96, 91, 140, 86, 66, 139, 235, 153, 184, 109, 224, 115, 117, 189, 251, 242, 245, 174, 138, 231, 160, 101, 212, 210, 177, 0, 64, 51, 238, 2, 17, 0, 0, 0, 4, 112, 96, 157, 3, 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