Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aabee23ee20233b0b725f626fae8cfb2c1d51079afcea1fa8958e051c0657236

Tx prefix hash: 431eb9ddef904c531a8c1f1ba855e0e8c2909fea4fc616a2d4f97f9d0c6d8c2a
Tx public key: 21da7b9714958beb6fe2e8aae5a956a7da27dd46efde7f3ad3795240b7f7f0ae
Timestamp: 1711863288 Timestamp [UCT]: 2024-03-31 05:34:48 Age [y:d:h:m:s]: 01:233:04:03:29
Block: 990116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 425316 RingCT/type: yes/0
Extra: 0121da7b9714958beb6fe2e8aae5a956a7da27dd46efde7f3ad3795240b7f7f0ae02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf10a40399c2a1c1d5a57f16cb84701394da2552bfb37d0baebbe615c43a7e77 0.600000000000 1450438 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": 990126, "vin": [ { "gen": { "height": 990116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf10a40399c2a1c1d5a57f16cb84701394da2552bfb37d0baebbe615c43a7e77" } } ], "extra": [ 1, 33, 218, 123, 151, 20, 149, 139, 235, 111, 226, 232, 170, 229, 169, 86, 167, 218, 39, 221, 70, 239, 222, 127, 58, 211, 121, 82, 64, 183, 247, 240, 174, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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