Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 113323bec7f269cb8ce16f35c67b4639d34322fe35d741d3f286612ec96b3a6c

Tx prefix hash: 99e79631aabaed22595b985e3d79ca34713e0f75baad3547c65ce5c7a192f2ab
Tx public key: d2b9264b9228d7698b4e7e1cad523128efdf7c5f1df4ccb0196bff2153647ebc
Timestamp: 1717719469 Timestamp [UCT]: 2024-06-07 00:17:49 Age [y:d:h:m:s]: 00:301:05:42:08
Block: 1038652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215278 RingCT/type: yes/0
Extra: 01d2b9264b9228d7698b4e7e1cad523128efdf7c5f1df4ccb0196bff2153647ebc02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66b50102b772fff5404e92407a6873e50e655f6ad4263e2b9b7136d38dce8732 0.600000000000 1507213 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": 1038662, "vin": [ { "gen": { "height": 1038652 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66b50102b772fff5404e92407a6873e50e655f6ad4263e2b9b7136d38dce8732" } } ], "extra": [ 1, 210, 185, 38, 75, 146, 40, 215, 105, 139, 78, 126, 28, 173, 82, 49, 40, 239, 223, 124, 95, 29, 244, 204, 176, 25, 107, 255, 33, 83, 100, 126, 188, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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