Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d25682cd6bbcc3f297006ef8f045707e87e9a7db4652d57097cd24380022acee

Tx prefix hash: 9cbd8af0afb9a11c5430814453d7fb2117accb64f212ea3f3b98950e6344cb46
Tx public key: 6fc83a7e38bb5d9f96fc5799c930608b2cf257474ed86166d3f1d6669eff4ce8
Timestamp: 1721453742 Timestamp [UCT]: 2024-07-20 05:35:42 Age [y:d:h:m:s]: 00:218:03:54:16
Block: 1069648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155758 RingCT/type: yes/0
Extra: 016fc83a7e38bb5d9f96fc5799c930608b2cf257474ed86166d3f1d6669eff4ce8021100000001162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66a3c42b78a93d9b9681d8031e9391f2c1cf3071ff4cf0d71c839a7ccf2fa86a 0.600000000000 1541145 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": 1069658, "vin": [ { "gen": { "height": 1069648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66a3c42b78a93d9b9681d8031e9391f2c1cf3071ff4cf0d71c839a7ccf2fa86a" } } ], "extra": [ 1, 111, 200, 58, 126, 56, 187, 93, 159, 150, 252, 87, 153, 201, 48, 96, 139, 44, 242, 87, 71, 78, 216, 97, 102, 211, 241, 214, 102, 158, 255, 76, 232, 2, 17, 0, 0, 0, 1, 22, 38, 19, 170, 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