Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 218ddb08dddf3845546486e2898e7278a5e2e975e379461e3081b5f1c92e0cba

Tx prefix hash: 332cc5fdac2d6cb13c29c36557e41c6cab3117d5a8463a40e904e3d66698e49c
Tx public key: ea34201d6a772f2c27cab5b052ffd62143984b36178c895e839f47fcbdcfb4ed
Timestamp: 1751137101 Timestamp [UCT]: 2025-06-28 18:58:21 Age [y:d:h:m:s]: 00:139:05:34:30
Block: 1314702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97604 RingCT/type: yes/0
Extra: 01ea34201d6a772f2c27cab5b052ffd62143984b36178c895e839f47fcbdcfb4ed0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c5c62af0fff44852ff337cb62fad92fe5e7b8384c0f4b69f6c79dfcf2413056 0.600000000000 1802353 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": 1314712, "vin": [ { "gen": { "height": 1314702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c5c62af0fff44852ff337cb62fad92fe5e7b8384c0f4b69f6c79dfcf2413056" } } ], "extra": [ 1, 234, 52, 32, 29, 106, 119, 47, 44, 39, 202, 181, 176, 82, 255, 214, 33, 67, 152, 75, 54, 23, 140, 137, 94, 131, 159, 71, 252, 189, 207, 180, 237, 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