Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b35c37668d60a6f15c83f775a22da2b68f16c5485cfb00e12b1550a1bd4d6ecf

Tx prefix hash: 4007279a80987f4895a41351160836c821e7257e66a03bdaafb9d8686e683a87
Tx public key: 47a07e0f2b1004b2f0edc1fbab83fecdf8204c60ec59b1eee1c86f571610ca83
Timestamp: 1588143669 Timestamp [UCT]: 2020-04-29 07:01:09 Age [y:d:h:m:s]: 04:212:03:44:25
Block: 96933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1065131 RingCT/type: yes/0
Extra: 0147a07e0f2b1004b2f0edc1fbab83fecdf8204c60ec59b1eee1c86f571610ca830211000000016fa03929000000000000000000

1 output(s) for total of 292.978795266000 dcy

stealth address amount amount idx
00: 0a359688fc2fd64602e468feca8b3ae9b54221a6a0764bd6232ca233c885deb9 292.978795266000 171846 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": 96943, "vin": [ { "gen": { "height": 96933 } } ], "vout": [ { "amount": 292978795266, "target": { "key": "0a359688fc2fd64602e468feca8b3ae9b54221a6a0764bd6232ca233c885deb9" } } ], "extra": [ 1, 71, 160, 126, 15, 43, 16, 4, 178, 240, 237, 193, 251, 171, 131, 254, 205, 248, 32, 76, 96, 236, 89, 177, 238, 225, 200, 111, 87, 22, 16, 202, 131, 2, 17, 0, 0, 0, 1, 111, 160, 57, 41, 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