Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1be6de57ca52b7f5f178972240fbd72df1d71357d9fc682051dcc1a4e8fefd8a

Tx prefix hash: fbc2f214bff7bfa21968d94b09e720391f90100750791322c29dfaec0abe65f2
Tx public key: 07d3ecdcca419f9001195da5c90326555bccab41a9a7bf6b250e545eb7b4c36c
Timestamp: 1750859146 Timestamp [UCT]: 2025-06-25 13:45:46 Age [y:d:h:m:s]: 00:142:03:00:07
Block: 1312548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99521 RingCT/type: yes/0
Extra: 0107d3ecdcca419f9001195da5c90326555bccab41a9a7bf6b250e545eb7b4c36c021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77ac9b18d5be66b1376e793892a1f3710f1d2e9bbaa3c1dcb4256f1338f5aad8 0.600000000000 1800181 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": 1312558, "vin": [ { "gen": { "height": 1312548 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77ac9b18d5be66b1376e793892a1f3710f1d2e9bbaa3c1dcb4256f1338f5aad8" } } ], "extra": [ 1, 7, 211, 236, 220, 202, 65, 159, 144, 1, 25, 93, 165, 201, 3, 38, 85, 91, 204, 171, 65, 169, 167, 191, 107, 37, 14, 84, 94, 183, 180, 195, 108, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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