Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65992a99456c8456cdaa7069083c6c02f98fcf7763b13e5e04c0f05898ce3f16

Tx prefix hash: 87c23f1b7b017ae66982c92044d69328dd419bf964bb84ffede5d1793d921454
Tx public key: 3a6954bb6463926d45d6089cfda90570b71a260825dbb0cddb7e8bca03f64fca
Timestamp: 1693578146 Timestamp [UCT]: 2023-09-01 14:22:26 Age [y:d:h:m:s]: 01:181:22:28:53
Block: 838686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391124 RingCT/type: yes/0
Extra: 013a6954bb6463926d45d6089cfda90570b71a260825dbb0cddb7e8bca03f64fca02110000000933af99f4000000000000000000

1 output(s) for total of 1.021139792000 dcy

stealth address amount amount idx
00: 3d901f211d4e14a34c1b2725a2a67d466e627c1fc0d464edfb1443de38efee6a 1.021139792000 1291456 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": 838696, "vin": [ { "gen": { "height": 838686 } } ], "vout": [ { "amount": 1021139792, "target": { "key": "3d901f211d4e14a34c1b2725a2a67d466e627c1fc0d464edfb1443de38efee6a" } } ], "extra": [ 1, 58, 105, 84, 187, 100, 99, 146, 109, 69, 214, 8, 156, 253, 169, 5, 112, 183, 26, 38, 8, 37, 219, 176, 205, 219, 126, 139, 202, 3, 246, 79, 202, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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