Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 990dd305bb6a3fb4e0ead64a0ba5c034adea059e75f11defdc31e2d865955c94

Tx prefix hash: 28a74f594ac505295b1906fe08993a47138554d948b6cce45ca5b44372ad7127
Tx public key: 0ff2c96ad505f66ff7cbd835fb8d52cda6508934b0f8d8dfc202bea105319e7d
Timestamp: 1752114807 Timestamp [UCT]: 2025-07-10 02:33:27 Age [y:d:h:m:s]: 00:198:16:45:30
Block: 1322329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140478 RingCT/type: yes/0
Extra: 010ff2c96ad505f66ff7cbd835fb8d52cda6508934b0f8d8dfc202bea105319e7d021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65caeebb36d51e7db7b6af887aea037e691172e1b54749b1015dfa5af9ab79c9 0.600000000000 1810056 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": 1322339, "vin": [ { "gen": { "height": 1322329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65caeebb36d51e7db7b6af887aea037e691172e1b54749b1015dfa5af9ab79c9" } } ], "extra": [ 1, 15, 242, 201, 106, 213, 5, 246, 111, 247, 203, 216, 53, 251, 141, 82, 205, 166, 80, 137, 52, 176, 248, 216, 223, 194, 2, 190, 161, 5, 49, 158, 125, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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