Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24389d17b3b8ca2b2945830f0fbc07007e2b24f67659fd5c36cd36e1c5a6ad49

Tx prefix hash: 791230db2ba01bb8da5770012b98d0e3c5dcb9f632905211965755c90277a423
Tx public key: 2d36a8496e7dfa8035b0b3229e572821d2c6c7e973b8627e79e2045836a65f15
Timestamp: 1755925264 Timestamp [UCT]: 2025-08-23 05:01:04 Age [y:d:h:m:s]: 00:090:15:10:35
Block: 1352470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64716 RingCT/type: yes/0
Extra: 012d36a8496e7dfa8035b0b3229e572821d2c6c7e973b8627e79e2045836a65f150211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d4875e97111d26e72bc8fa8158ab472a2432ea75b2af7e97dba31f8e979e424 0.600000000000 1840435 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": 1352480, "vin": [ { "gen": { "height": 1352470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d4875e97111d26e72bc8fa8158ab472a2432ea75b2af7e97dba31f8e979e424" } } ], "extra": [ 1, 45, 54, 168, 73, 110, 125, 250, 128, 53, 176, 179, 34, 158, 87, 40, 33, 210, 198, 199, 233, 115, 184, 98, 126, 121, 226, 4, 88, 54, 166, 95, 21, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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