Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f49ad6bc87d977d390500bd4b029af62c1ebd445aeccb620e45a1b4139c9ed21

Tx prefix hash: a8072aa7d65384c6c1d5478857127652c94cb4bbd8ce6bd703cfa5a014027893
Tx public key: f09dd0b2cac871fba06ef4381c56c073a6ad796299dc6b12fca95b75e707db42
Timestamp: 1709183110 Timestamp [UCT]: 2024-02-29 05:05:10 Age [y:d:h:m:s]: 00:342:13:07:21
Block: 967880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244930 RingCT/type: yes/0
Extra: 01f09dd0b2cac871fba06ef4381c56c073a6ad796299dc6b12fca95b75e707db420211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14cf6ba313f22b9e93827acc369f9b1ba7f8ef6a90cdea15456ff748357eb30b 0.600000000000 1427671 of 15

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": 967890, "vin": [ { "gen": { "height": 967880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14cf6ba313f22b9e93827acc369f9b1ba7f8ef6a90cdea15456ff748357eb30b" } } ], "extra": [ 1, 240, 157, 208, 178, 202, 200, 113, 251, 160, 110, 244, 56, 28, 86, 192, 115, 166, 173, 121, 98, 153, 220, 107, 18, 252, 169, 91, 117, 231, 7, 219, 66, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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