Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c05ec10ee0964129a9f5620e4ff0249b84ff01b30cd84300f5c503a0370ec49c

Tx prefix hash: c90dab5f4f6caed40a36bce13ebcdf0ee22661b68b8e29955bc621a528f79902
Tx public key: 046c8407c0d1e361ef82231748e6f2aacd003b403f6859baffbf260abfe906d4
Timestamp: 1630768438 Timestamp [UCT]: 2021-09-04 15:13:58 Age [y:d:h:m:s]: 02:302:17:08:55
Block: 327380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 730133 RingCT/type: yes/0
Extra: 01046c8407c0d1e361ef82231748e6f2aacd003b403f6859baffbf260abfe906d402110000001f51fa4013000000000000000000

1 output(s) for total of 50.495724587000 dcy

stealth address amount amount idx
00: 1060dff59a0d16eccd368a57e3f99652327cb2a06364f735b08554d9e6782d0f 50.495724587000 678009 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": 327390, "vin": [ { "gen": { "height": 327380 } } ], "vout": [ { "amount": 50495724587, "target": { "key": "1060dff59a0d16eccd368a57e3f99652327cb2a06364f735b08554d9e6782d0f" } } ], "extra": [ 1, 4, 108, 132, 7, 192, 209, 227, 97, 239, 130, 35, 23, 72, 230, 242, 170, 205, 0, 59, 64, 63, 104, 89, 186, 255, 191, 38, 10, 191, 233, 6, 212, 2, 17, 0, 0, 0, 31, 81, 250, 64, 19, 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