Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 853a019100dce7955b33c719c7ca3eccfb1958ba039bbd6b810623710ae4720a

Tx prefix hash: bc8c6a087cf228dbe2545c09d86679ba1e5f7d4be9521f01cb574a6b24c506cf
Tx public key: 41792cfa46797cd9f7f5943a647ebbad6b0aba1035cb15ceec5294bc8a8b2975
Timestamp: 1649750299 Timestamp [UCT]: 2022-04-12 07:58:19 Age [y:d:h:m:s]: 02:338:15:22:57
Block: 478474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 761700 RingCT/type: yes/0
Extra: 0141792cfa46797cd9f7f5943a647ebbad6b0aba1035cb15ceec5294bc8a8b2975021100000002cb8520c2000000000000000000

1 output(s) for total of 15.944732993000 dcy

stealth address amount amount idx
00: b97a6523606a8efd4d4a256aec290e337bbd3a3a50764d80d016e43e529b8a2e 15.944732993000 899243 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": 478484, "vin": [ { "gen": { "height": 478474 } } ], "vout": [ { "amount": 15944732993, "target": { "key": "b97a6523606a8efd4d4a256aec290e337bbd3a3a50764d80d016e43e529b8a2e" } } ], "extra": [ 1, 65, 121, 44, 250, 70, 121, 124, 217, 247, 245, 148, 58, 100, 126, 187, 173, 107, 10, 186, 16, 53, 203, 21, 206, 236, 82, 148, 188, 138, 139, 41, 117, 2, 17, 0, 0, 0, 2, 203, 133, 32, 194, 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