Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd6f0082808370cf98de3c822cfafd8cd8c0f20378611ac22ca9672e60d6ab4b

Tx prefix hash: b6434375bbc4538ab6667ec6fcbfb0c37bcdf656cbcb5a353ebb8e13f7b9b68e
Tx public key: 7b87615fec9b8bd12b7931dc04f0f4413d61c43afc3d72a73b40a27cb55481af
Timestamp: 1674158171 Timestamp [UCT]: 2023-01-19 19:56:11 Age [y:d:h:m:s]: 02:105:18:33:34
Block: 678369 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 597271 RingCT/type: yes/0
Extra: 017b87615fec9b8bd12b7931dc04f0f4413d61c43afc3d72a73b40a27cb55481af02110000000152542ceb000000000000000000

1 output(s) for total of 3.469619449000 dcy

stealth address amount amount idx
00: 3e97666eb836b65e50ac9e5f1f9a7f5f5d6d02b2cea22d2120c57bd38bccf301 3.469619449000 1120242 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": 678379, "vin": [ { "gen": { "height": 678369 } } ], "vout": [ { "amount": 3469619449, "target": { "key": "3e97666eb836b65e50ac9e5f1f9a7f5f5d6d02b2cea22d2120c57bd38bccf301" } } ], "extra": [ 1, 123, 135, 97, 95, 236, 155, 139, 209, 43, 121, 49, 220, 4, 240, 244, 65, 61, 97, 196, 58, 252, 61, 114, 167, 59, 64, 162, 124, 181, 84, 129, 175, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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