Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 334af3623fc993c11b92d23c6cafd2396bea45c7c31cbc2128c064ee3b1caabe

Tx prefix hash: b2d8eb0f5c81e2f8e2c484663b3960e77ffbbbed72727296570d7c904cbc7c06
Tx public key: 29e22f6148505801e479a457240b5f513fae35677638c578913cb84556c41095
Timestamp: 1648271914 Timestamp [UCT]: 2022-03-26 05:18:34 Age [y:d:h:m:s]: 03:036:10:36:10
Block: 466588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 806232 RingCT/type: yes/0
Extra: 0129e22f6148505801e479a457240b5f513fae35677638c578913cb84556c4109502110000000306faf294000000000000000000

1 output(s) for total of 17.458242456000 dcy

stealth address amount amount idx
00: dc106a9694f7a959d7ce518cec6e196f09424c0a8e1bad079f7ac38db011774f 17.458242456000 884931 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": 466598, "vin": [ { "gen": { "height": 466588 } } ], "vout": [ { "amount": 17458242456, "target": { "key": "dc106a9694f7a959d7ce518cec6e196f09424c0a8e1bad079f7ac38db011774f" } } ], "extra": [ 1, 41, 226, 47, 97, 72, 80, 88, 1, 228, 121, 164, 87, 36, 11, 95, 81, 63, 174, 53, 103, 118, 56, 197, 120, 145, 60, 184, 69, 86, 196, 16, 149, 2, 17, 0, 0, 0, 3, 6, 250, 242, 148, 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