Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9172a33ea09c666cbc49e3d9df80a23f3ecf4d287d9b65d3b3dc9bdbce8792d0

Tx prefix hash: 831bcbd81bc38a8dabd10a65e0d395acde1a78d28d4fc6bfc048911c3defbb32
Tx public key: c0a76f122f1f528de91474eace84d015c97e306b7f420d3021f29615ee973b05
Timestamp: 1718005467 Timestamp [UCT]: 2024-06-10 07:44:27 Age [y:d:h:m:s]: 00:228:17:17:25
Block: 1041023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163640 RingCT/type: yes/0
Extra: 01c0a76f122f1f528de91474eace84d015c97e306b7f420d3021f29615ee973b050211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ca70524e4f96d66fa85d7b0abf8e2f7eb15b2ef457f915f44dd70b834dbb665 0.600000000000 1509688 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": 1041033, "vin": [ { "gen": { "height": 1041023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ca70524e4f96d66fa85d7b0abf8e2f7eb15b2ef457f915f44dd70b834dbb665" } } ], "extra": [ 1, 192, 167, 111, 18, 47, 31, 82, 141, 233, 20, 116, 234, 206, 132, 208, 21, 201, 126, 48, 107, 127, 66, 13, 48, 33, 242, 150, 21, 238, 151, 59, 5, 2, 17, 0, 0, 0, 3, 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