Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b173a01e9bb66828dbb2a0cd14e83584aa77201a00378eb134c63686a42b9170

Tx prefix hash: 3dd79bbfef6e409fd0d6d80cbde38a70b7870e78d77be9d871766928ad439b0e
Tx public key: c33b7851586dcaef12a055c73f3a130e65b7d11340d302cffb2f15472c0ff6ec
Timestamp: 1715784746 Timestamp [UCT]: 2024-05-15 14:52:26 Age [y:d:h:m:s]: 00:337:03:54:50
Block: 1022616 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240977 RingCT/type: yes/0
Extra: 01c33b7851586dcaef12a055c73f3a130e65b7d11340d302cffb2f15472c0ff6ec0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.607840000000 dcy

stealth address amount amount idx
00: de1346ff0c016b307f4091d4fd10eff4b7b609841b520749d8ff7a9f3587f8ea 0.607840000000 1487269 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": 1022626, "vin": [ { "gen": { "height": 1022616 } } ], "vout": [ { "amount": 607840000, "target": { "key": "de1346ff0c016b307f4091d4fd10eff4b7b609841b520749d8ff7a9f3587f8ea" } } ], "extra": [ 1, 195, 59, 120, 81, 88, 109, 202, 239, 18, 160, 85, 199, 63, 58, 19, 14, 101, 183, 209, 19, 64, 211, 2, 207, 251, 47, 21, 71, 44, 15, 246, 236, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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