Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d554faaa7bf2fd9d89dfb64c717cbe9192ca185e89aa9f14844a3a6d066b2fb

Tx prefix hash: ee24c762d2881fc946020110bef7b81d8757dc976b44ef8e8b77d510c65a8975
Tx public key: e58148378de9465100fa5bd1d7ca24e85b385c0d96110fd3ec105bef286a27bb
Timestamp: 1702581293 Timestamp [UCT]: 2023-12-14 19:14:53 Age [y:d:h:m:s]: 01:109:05:42:11
Block: 913140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339200 RingCT/type: yes/0
Extra: 01e58148378de9465100fa5bd1d7ca24e85b385c0d96110fd3ec105bef286a27bb02110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56e7e2b75a7e915a7629d7c024df40260de94677c6ea1d4b828de879ff657cf1 0.600000000000 1370386 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": 913150, "vin": [ { "gen": { "height": 913140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56e7e2b75a7e915a7629d7c024df40260de94677c6ea1d4b828de879ff657cf1" } } ], "extra": [ 1, 229, 129, 72, 55, 141, 233, 70, 81, 0, 250, 91, 209, 215, 202, 36, 232, 91, 56, 92, 13, 150, 17, 15, 211, 236, 16, 91, 239, 40, 106, 39, 187, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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