Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c4672167b90d708db09432ad1c943d3f3fcc35e30ea1a2b8299905b1a744246

Tx prefix hash: 9409fb639ca4ad2aa858706fde841c4a53ee2a4cce3d30e14a66042c18ff1711
Tx public key: 5630d7824b941a41c3be6a181790b1eb0995a8d0583b1b0dc6c5d56ebf6c6bae
Timestamp: 1581486878 Timestamp [UCT]: 2020-02-12 05:54:38 Age [y:d:h:m:s]: 05:056:22:50:45
Block: 63313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1193425 RingCT/type: yes/0
Extra: 015630d7824b941a41c3be6a181790b1eb0995a8d0583b1b0dc6c5d56ebf6c6bae0211000000394943cd9f000000000000000000

1 output(s) for total of 378.633086757000 dcy

stealth address amount amount idx
00: 6cd634e52a52a6a811442523abfac88334c58704a6192d2c378d5f8d0e396501 378.633086757000 116735 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": 63323, "vin": [ { "gen": { "height": 63313 } } ], "vout": [ { "amount": 378633086757, "target": { "key": "6cd634e52a52a6a811442523abfac88334c58704a6192d2c378d5f8d0e396501" } } ], "extra": [ 1, 86, 48, 215, 130, 75, 148, 26, 65, 195, 190, 106, 24, 23, 144, 177, 235, 9, 149, 168, 208, 88, 59, 27, 13, 198, 197, 213, 110, 191, 108, 107, 174, 2, 17, 0, 0, 0, 57, 73, 67, 205, 159, 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