Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f39c8ee7fe395950dfeb12a487aaee98bb3c71e2b4e3649f6a3ad614e53de9a3

Tx prefix hash: 2560b7c70216174bf6689640aed170679ef7504be9ed3aa21ebfb444a79c66bb
Tx public key: e3ba66e8147b17468b08bb7515cb430ae4b2b440b598b3cd48fae8e408a4d9d2
Timestamp: 1739027818 Timestamp [UCT]: 2025-02-08 15:16:58 Age [y:d:h:m:s]: 00:350:00:48:44
Block: 1214875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247831 RingCT/type: yes/0
Extra: 01e3ba66e8147b17468b08bb7515cb430ae4b2b440b598b3cd48fae8e408a4d9d2021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8de621bdb49cb713b50b674f22bd6888e51847c1632610ff8787d9f4b8c0a403 0.600000000000 1701670 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": 1214885, "vin": [ { "gen": { "height": 1214875 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8de621bdb49cb713b50b674f22bd6888e51847c1632610ff8787d9f4b8c0a403" } } ], "extra": [ 1, 227, 186, 102, 232, 20, 123, 23, 70, 139, 8, 187, 117, 21, 203, 67, 10, 228, 178, 180, 64, 181, 152, 179, 205, 72, 250, 232, 228, 8, 164, 217, 210, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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