Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b52e26ce874431bf3ce95402680f01b7566db1fd49423bb192e2fd9fd79f361d

Tx prefix hash: 7f82b093ff265665a8e4f96cb8388dd32fd8ff30048f4ac1b74f70689d8ceb7e
Tx public key: a0538cba2971b791481b5ac3765c1025fa5a26a622062e68ff604551b4e9d7c4
Timestamp: 1745411962 Timestamp [UCT]: 2025-04-23 12:39:22 Age [y:d:h:m:s]: 00:211:06:18:58
Block: 1267714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148716 RingCT/type: yes/0
Extra: 01a0538cba2971b791481b5ac3765c1025fa5a26a622062e68ff604551b4e9d7c4021100000005dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0d2c21b442e9881b8ff6018c205072a732f6e23ba0b15ea83f8f99a5118c572 0.600000000000 1754943 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": 1267724, "vin": [ { "gen": { "height": 1267714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0d2c21b442e9881b8ff6018c205072a732f6e23ba0b15ea83f8f99a5118c572" } } ], "extra": [ 1, 160, 83, 140, 186, 41, 113, 183, 145, 72, 27, 90, 195, 118, 92, 16, 37, 250, 90, 38, 166, 34, 6, 46, 104, 255, 96, 69, 81, 180, 233, 215, 196, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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