Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d433732ac7bbfc155f89ed55a012bb4eed49b1afdb28dbcce145049d273261d

Tx prefix hash: 43b24031892da815922fc349793352c44b89dd1763ebfa60f9c382bb58fd3840
Tx public key: 563c662303d9a4ccc46c3401f0aa4f9f6a5f2f15b3d7c4bc22936783a7acbc0a
Timestamp: 1717754898 Timestamp [UCT]: 2024-06-07 10:08:18 Age [y:d:h:m:s]: 00:283:02:36:05
Block: 1038949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202328 RingCT/type: yes/0
Extra: 01563c662303d9a4ccc46c3401f0aa4f9f6a5f2f15b3d7c4bc22936783a7acbc0a021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a869321a7b69e8b867452d980502fcdc2cf4be4354ee7b12235dca6ac986596 0.600000000000 1507522 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": 1038959, "vin": [ { "gen": { "height": 1038949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a869321a7b69e8b867452d980502fcdc2cf4be4354ee7b12235dca6ac986596" } } ], "extra": [ 1, 86, 60, 102, 35, 3, 217, 164, 204, 196, 108, 52, 1, 240, 170, 79, 159, 106, 95, 47, 21, 179, 215, 196, 188, 34, 147, 103, 131, 167, 172, 188, 10, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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