Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13f8b2afed73477fc698f778cf14f615bc1abfb6ca13c8972f36b58c104f6a13

Tx prefix hash: 49829121009941e8d86a9e7f35ac77b757f0edfbed711cb6e9beb6c0a1bde363
Tx public key: edfda2cd1c266206b0cc9ba2d521790e850dfb49f0f88a910a63a7a660fe49da
Timestamp: 1751499311 Timestamp [UCT]: 2025-07-02 23:35:11 Age [y:d:h:m:s]: 00:132:01:03:12
Block: 1317541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92624 RingCT/type: yes/0
Extra: 01edfda2cd1c266206b0cc9ba2d521790e850dfb49f0f88a910a63a7a660fe49da021100000001bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43d2e8f79e009738ff241652f56cd4d4010f9a0978be7eab2ca8052040745129 0.600000000000 1805210 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": 1317551, "vin": [ { "gen": { "height": 1317541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43d2e8f79e009738ff241652f56cd4d4010f9a0978be7eab2ca8052040745129" } } ], "extra": [ 1, 237, 253, 162, 205, 28, 38, 98, 6, 176, 204, 155, 162, 213, 33, 121, 14, 133, 13, 251, 73, 240, 248, 138, 145, 10, 99, 167, 166, 96, 254, 73, 218, 2, 17, 0, 0, 0, 1, 191, 81, 178, 162, 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