Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77ec4b8662b1a3c53da71e7d64b37dd9dcd3098db6844e1351a95025fe2c2dd1

Tx prefix hash: e266368add55693d3e4b8d4e475740bacbf5746f9c3dd729e925162f64b43e5c
Tx public key: 043806fdc43461e362c71fd51e38b98ace5c3f1b672e39e019d86e10973dd307
Timestamp: 1751290619 Timestamp [UCT]: 2025-06-30 13:36:59 Age [y:d:h:m:s]: 00:143:10:04:46
Block: 1315872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100693 RingCT/type: yes/0
Extra: 01043806fdc43461e362c71fd51e38b98ace5c3f1b672e39e019d86e10973dd30702110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c03933af1d3d6745edd9cc16528602fe26e6f3a29dc2839e4ac62fc058153ce6 0.600000000000 1803529 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": 1315882, "vin": [ { "gen": { "height": 1315872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c03933af1d3d6745edd9cc16528602fe26e6f3a29dc2839e4ac62fc058153ce6" } } ], "extra": [ 1, 4, 56, 6, 253, 196, 52, 97, 227, 98, 199, 31, 213, 30, 56, 185, 138, 206, 92, 63, 27, 103, 46, 57, 224, 25, 216, 110, 16, 151, 61, 211, 7, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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