Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 777484ef1b38b182ae081076ac45c2b0366628bbe7330db93217209aeb0ec2f1

Tx prefix hash: f83d800790b1e96c9485e0384edfa88bd816180de53b8d7f5a8d09e28c4cd0dd
Tx public key: caf6c62db9afc9d6228e93fbf3c03f9d96b296086bec26e4ed057d5e294aa50a
Timestamp: 1745938482 Timestamp [UCT]: 2025-04-29 14:54:42 Age [y:d:h:m:s]: 00:012:06:54:52
Block: 1272091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8776 RingCT/type: yes/0
Extra: 01caf6c62db9afc9d6228e93fbf3c03f9d96b296086bec26e4ed057d5e294aa50a0211000000081f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a4047c0a3662502536673830b6fb80d56162e5d4ead8a4e46c5d12859745278 0.600000000000 1759364 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": 1272101, "vin": [ { "gen": { "height": 1272091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a4047c0a3662502536673830b6fb80d56162e5d4ead8a4e46c5d12859745278" } } ], "extra": [ 1, 202, 246, 198, 45, 185, 175, 201, 214, 34, 142, 147, 251, 243, 192, 63, 157, 150, 178, 150, 8, 107, 236, 38, 228, 237, 5, 125, 94, 41, 74, 165, 10, 2, 17, 0, 0, 0, 8, 31, 144, 81, 122, 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