Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66cfd7ce6067b8fb19830ba4af5c90a85aadef517e7b87c2f295fa42533766f2

Tx prefix hash: 2a643a3f57e2eacd57149403ec06f058af4cb4d2c2216f65874a15374a708dfb
Tx public key: 2f318b6b1f98883e0735f095411615d178324e3dc93c6390be7f335224b40daf
Timestamp: 1725210429 Timestamp [UCT]: 2024-09-01 17:07:09 Age [y:d:h:m:s]: 00:215:03:14:59
Block: 1100753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153597 RingCT/type: yes/0
Extra: 012f318b6b1f98883e0735f095411615d178324e3dc93c6390be7f335224b40daf02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b786ddcdcb905bb9231baee596c205ea3bfa209ddc53306b5e060f6c7e37411 0.600000000000 1576734 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": 1100763, "vin": [ { "gen": { "height": 1100753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b786ddcdcb905bb9231baee596c205ea3bfa209ddc53306b5e060f6c7e37411" } } ], "extra": [ 1, 47, 49, 139, 107, 31, 152, 136, 62, 7, 53, 240, 149, 65, 22, 21, 209, 120, 50, 78, 61, 201, 60, 99, 144, 190, 127, 51, 82, 36, 180, 13, 175, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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