Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e87359ea0ba2cf86397d1c4031e16c06d41e35801b926ca43ca5ac8e4c6f4b7

Tx prefix hash: 3f65945575a48ab2a3c9837df4c2a037031fca45e7fe5cb683357a69e65bf49e
Tx public key: e76bb8536d0e966dec411bbc8f2a47efc953ead57a0958c48597aa9976c1329d
Timestamp: 1722808617 Timestamp [UCT]: 2024-08-04 21:56:57 Age [y:d:h:m:s]: 00:226:12:22:41
Block: 1080835 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161805 RingCT/type: yes/0
Extra: 01e76bb8536d0e966dec411bbc8f2a47efc953ead57a0958c48597aa9976c1329d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 548d1fdd23dd812fc1f53e5a50e175ae3ce110b08c85ada8cceeb7705ca3877d 0.600000000000 1554350 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": 1080845, "vin": [ { "gen": { "height": 1080835 } } ], "vout": [ { "amount": 600000000, "target": { "key": "548d1fdd23dd812fc1f53e5a50e175ae3ce110b08c85ada8cceeb7705ca3877d" } } ], "extra": [ 1, 231, 107, 184, 83, 109, 14, 150, 109, 236, 65, 27, 188, 143, 42, 71, 239, 201, 83, 234, 213, 122, 9, 88, 196, 133, 151, 170, 153, 118, 193, 50, 157, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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