Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2a9114cb4be1768f2217f08f0d935b9cb66f1c135af9b14af9e07ceea710891

Tx prefix hash: bb1d068d4accb07d57522a02210820896a26edd9cb1f6fa5fa5121d2c77c5c94
Tx public key: 043a50490aeab2a874e7f0df51d75fc7871c768c4c2b8073e75315b3960edd23
Timestamp: 1713629789 Timestamp [UCT]: 2024-04-20 16:16:29 Age [y:d:h:m:s]: 00:350:04:19:40
Block: 1004732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250347 RingCT/type: yes/0
Extra: 01043a50490aeab2a874e7f0df51d75fc7871c768c4c2b8073e75315b3960edd230211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6be4f68a21fc55e494d9df8e066770d25d5bfa4b138d795ec5cf71f7bff8f2dc 0.600000000000 1465304 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": 1004742, "vin": [ { "gen": { "height": 1004732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6be4f68a21fc55e494d9df8e066770d25d5bfa4b138d795ec5cf71f7bff8f2dc" } } ], "extra": [ 1, 4, 58, 80, 73, 10, 234, 178, 168, 116, 231, 240, 223, 81, 215, 95, 199, 135, 28, 118, 140, 76, 43, 128, 115, 231, 83, 21, 179, 150, 14, 221, 35, 2, 17, 0, 0, 0, 9, 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