Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 488bf245b6b93ebfa0604f7f42b1ced8b832ecf3e26e4b7c4157bc82c3fc5f41

Tx prefix hash: 9fdbda5471a3430762fc3c3a5eea42544b0eb4ef2a4845ea0fc89e6332f609f5
Tx public key: 816857d94e308fa0dc76e6e247bccf81ce7350a5fd596723467d002c0304bbb6
Timestamp: 1636277970 Timestamp [UCT]: 2021-11-07 09:39:30 Age [y:d:h:m:s]: 03:128:06:26:50
Block: 369189 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 870044 RingCT/type: yes/0
Extra: 01816857d94e308fa0dc76e6e247bccf81ce7350a5fd596723467d002c0304bbb60211000000284f792ffd000000000000000000

1 output(s) for total of 36.704894560000 dcy

stealth address amount amount idx
00: 0d08e2fc96fe6f998d5ef5d761cc8787867d19daea6d84119738234f8ba17b01 36.704894560000 748667 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": 369199, "vin": [ { "gen": { "height": 369189 } } ], "vout": [ { "amount": 36704894560, "target": { "key": "0d08e2fc96fe6f998d5ef5d761cc8787867d19daea6d84119738234f8ba17b01" } } ], "extra": [ 1, 129, 104, 87, 217, 78, 48, 143, 160, 220, 118, 230, 226, 71, 188, 207, 129, 206, 115, 80, 165, 253, 89, 103, 35, 70, 125, 0, 44, 3, 4, 187, 182, 2, 17, 0, 0, 0, 40, 79, 121, 47, 253, 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