Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbc6916a60618928bc064d8c31b2a4d2ce22033db5c8675a1d947c14be2ac0bd

Tx prefix hash: 6f1d5c60ab3586ab27b1008bfc98e00b03d6b9385e1bd2dba33a918ca67e8e62
Tx public key: 7e50aece57676959e5b1fdffbc5c338a1e8cca35fd5eb36c171aa474b824c04e
Timestamp: 1581950594 Timestamp [UCT]: 2020-02-17 14:43:14 Age [y:d:h:m:s]: 04:316:05:15:19
Block: 66912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118316 RingCT/type: yes/0
Extra: 017e50aece57676959e5b1fdffbc5c338a1e8cca35fd5eb36c171aa474b824c04e021100000001c71d3ff9000000000000000000

1 output(s) for total of 368.377906719000 dcy

stealth address amount amount idx
00: b68ea88fe1e05eb2ef5e8e6338d8dba0c5b211bd769696b7a2428f3e6592cbca 368.377906719000 123163 of 0

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": 66922, "vin": [ { "gen": { "height": 66912 } } ], "vout": [ { "amount": 368377906719, "target": { "key": "b68ea88fe1e05eb2ef5e8e6338d8dba0c5b211bd769696b7a2428f3e6592cbca" } } ], "extra": [ 1, 126, 80, 174, 206, 87, 103, 105, 89, 229, 177, 253, 255, 188, 92, 51, 138, 30, 140, 202, 53, 253, 94, 179, 108, 23, 26, 164, 116, 184, 36, 192, 78, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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