Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aeff6cfc7e1d32bfa94119ff85f3aea0db1c24cedfea0f6d6049d5ff6392325a

Tx prefix hash: 8d252730bf4967de0ea9e0325c7d33a22f66412e7c61ccdcd4c92190bd6a33fa
Tx public key: 0011d62be3d326c0e733b0f5cd73157194af94465b60d22c4ece541776792a6f
Timestamp: 1745792373 Timestamp [UCT]: 2025-04-27 22:19:33 Age [y:d:h:m:s]: 00:012:02:59:41
Block: 1270877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8665 RingCT/type: yes/0
Extra: 010011d62be3d326c0e733b0f5cd73157194af94465b60d22c4ece541776792a6f0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b76efe92fb007f6b5dd99c4f4876594fc7a4c8c9bcfb7d080e79cc1027126eb6 0.600000000000 1758122 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": 1270887, "vin": [ { "gen": { "height": 1270877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b76efe92fb007f6b5dd99c4f4876594fc7a4c8c9bcfb7d080e79cc1027126eb6" } } ], "extra": [ 1, 0, 17, 214, 43, 227, 211, 38, 192, 231, 51, 176, 245, 205, 115, 21, 113, 148, 175, 148, 70, 91, 96, 210, 44, 78, 206, 84, 23, 118, 121, 42, 111, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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