Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bdaf9d6ed4a1d95f9239ff16cb33c9f01ad34e5226191cfc102b942e9a5da9d

Tx prefix hash: 4cd9c2d94d44b467261a04f33ec416c375af6e6422d7eb4d79535e569ced2fcf
Tx public key: eacf802ca5db9fb0e2e877bf2fe38a8de6d91962f938d3c380be90e27ab564f9
Timestamp: 1755050561 Timestamp [UCT]: 2025-08-13 02:02:41 Age [y:d:h:m:s]: 00:048:17:30:37
Block: 1345775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34146 RingCT/type: yes/0
Extra: 01eacf802ca5db9fb0e2e877bf2fe38a8de6d91962f938d3c380be90e27ab564f90211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56c27381a43537739ed981408f57f1872eeba0a4181e7a3352fff5bf5e64e11f 0.600000000000 1833670 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": 1345785, "vin": [ { "gen": { "height": 1345775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56c27381a43537739ed981408f57f1872eeba0a4181e7a3352fff5bf5e64e11f" } } ], "extra": [ 1, 234, 207, 128, 44, 165, 219, 159, 176, 226, 232, 119, 191, 47, 227, 138, 141, 230, 217, 25, 98, 249, 56, 211, 195, 128, 190, 144, 226, 122, 181, 100, 249, 2, 17, 0, 0, 0, 1, 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