Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf8cfd09ff6c1759405287fa1113d1cbe30cdfe97ca3f1f6c73373fad71abe47

Tx prefix hash: 0c0c11a94756611da51bdf71da115a17bfac41864bbf7ece0e4ebdb24858e0fc
Tx public key: 5c4c0bd25e886c315af062b4353a072cf96a6dcbb5bb3b5ceb27d7beb77a9e52
Timestamp: 1723005652 Timestamp [UCT]: 2024-08-07 04:40:52 Age [y:d:h:m:s]: 00:236:13:47:40
Block: 1082470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168971 RingCT/type: yes/0
Extra: 015c4c0bd25e886c315af062b4353a072cf96a6dcbb5bb3b5ceb27d7beb77a9e5202110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ee7646b47d86b6629bf1ee30e973296fd0eeded886954c599f30c366ad0ab1d 0.600000000000 1556297 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": 1082480, "vin": [ { "gen": { "height": 1082470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ee7646b47d86b6629bf1ee30e973296fd0eeded886954c599f30c366ad0ab1d" } } ], "extra": [ 1, 92, 76, 11, 210, 94, 136, 108, 49, 90, 240, 98, 180, 53, 58, 7, 44, 249, 106, 109, 203, 181, 187, 59, 92, 235, 39, 215, 190, 183, 122, 158, 82, 2, 17, 0, 0, 0, 4, 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