Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abed229c37e6bf459ff07591bfbdcddcd602488d5213a88acf6b7e8db57dbe38

Tx prefix hash: 9df52299f8def9631b822007c123a01e8aa3a55e20f25003e4042c90f367a690
Tx public key: 421be1f4b6991ac6938696d35887dc39b1a0820f72c4a33bf8ff9a81ac7257ea
Timestamp: 1738135634 Timestamp [UCT]: 2025-01-29 07:27:14 Age [y:d:h:m:s]: 01:000:04:29:40
Block: 1207490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258680 RingCT/type: yes/0
Extra: 01421be1f4b6991ac6938696d35887dc39b1a0820f72c4a33bf8ff9a81ac7257ea0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7d89c41b2c02de31b9a8a5768307559c055066bf3f93b8c89ab6d2b32530a78 0.600000000000 1694213 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": 1207500, "vin": [ { "gen": { "height": 1207490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7d89c41b2c02de31b9a8a5768307559c055066bf3f93b8c89ab6d2b32530a78" } } ], "extra": [ 1, 66, 27, 225, 244, 182, 153, 26, 198, 147, 134, 150, 211, 88, 135, 220, 57, 177, 160, 130, 15, 114, 196, 163, 59, 248, 255, 154, 129, 172, 114, 87, 234, 2, 17, 0, 0, 0, 5, 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