Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9aa23c9987ad5ef11317dcb5465d5ba413fd7dacb7555c2d7f032f686efbb22

Tx prefix hash: f479e235c81d5aef0e0720486855bdb20fcb89ce9b239fa0749603ec78848986
Tx public key: be29a166f2a0cbcb4db835be9ab7cd78d0f8df879a46080b41767ee0ef0db7cf
Timestamp: 1742906448 Timestamp [UCT]: 2025-03-25 12:40:48 Age [y:d:h:m:s]: 00:254:20:47:23
Block: 1246976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179924 RingCT/type: yes/0
Extra: 01be29a166f2a0cbcb4db835be9ab7cd78d0f8df879a46080b41767ee0ef0db7cf02110000000324ff4ea1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5758022e29e1a3aefcf23c72bcccd063c28ef8f333cc9e2ca8c5d36f20d5bcc 0.600000000000 1733977 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": 1246986, "vin": [ { "gen": { "height": 1246976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5758022e29e1a3aefcf23c72bcccd063c28ef8f333cc9e2ca8c5d36f20d5bcc" } } ], "extra": [ 1, 190, 41, 161, 102, 242, 160, 203, 203, 77, 184, 53, 190, 154, 183, 205, 120, 208, 248, 223, 135, 154, 70, 8, 11, 65, 118, 126, 224, 239, 13, 183, 207, 2, 17, 0, 0, 0, 3, 36, 255, 78, 161, 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