Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c97963aa6370528460fa8946c08694fa81e4b52e2477f11f5a0e57e9bfa5323

Tx prefix hash: e1580210e4c4c7c35b096d5d1dd1d0d67c1cc63b07e4d61e09f0ba048f6dd641
Tx public key: 300f6264a718b21a65068a88f9f70dda2f0df2af4d8a275cf1cbccdc724d0436
Timestamp: 1742440162 Timestamp [UCT]: 2025-03-20 03:09:22 Age [y:d:h:m:s]: 00:066:08:17:23
Block: 1243136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47447 RingCT/type: yes/0
Extra: 01300f6264a718b21a65068a88f9f70dda2f0df2af4d8a275cf1cbccdc724d0436021100000008ed95dce7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb737833f6f89aed0156c4a7b9690f0fa853205f20b16ad7fc3a36065e88a51d 0.600000000000 1730121 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": 1243146, "vin": [ { "gen": { "height": 1243136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb737833f6f89aed0156c4a7b9690f0fa853205f20b16ad7fc3a36065e88a51d" } } ], "extra": [ 1, 48, 15, 98, 100, 167, 24, 178, 26, 101, 6, 138, 136, 249, 247, 13, 218, 47, 13, 242, 175, 77, 138, 39, 92, 241, 203, 204, 220, 114, 77, 4, 54, 2, 17, 0, 0, 0, 8, 237, 149, 220, 231, 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