Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e38bb084cab6c540802b216aa03e64113b504b1ce04922dae77f05740c2ce377

Tx prefix hash: 336c0408c7b728226ff0bc3fab2433bb7a98ea079507c82619a73d725062f98d
Tx public key: 643a894db9414e47239bb06dc36fa1e8c3e25886493c0bd73fdb582602af0ed5
Timestamp: 1744423596 Timestamp [UCT]: 2025-04-12 02:06:36 Age [y:d:h:m:s]: 00:223:12:56:50
Block: 1259545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157475 RingCT/type: yes/0
Extra: 01643a894db9414e47239bb06dc36fa1e8c3e25886493c0bd73fdb582602af0ed50211000000036c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4da9125dfeca4350751239fe1904a4a5e71dc27668b9805f8c146277a0ae5c0b 0.600000000000 1746692 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": 1259555, "vin": [ { "gen": { "height": 1259545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4da9125dfeca4350751239fe1904a4a5e71dc27668b9805f8c146277a0ae5c0b" } } ], "extra": [ 1, 100, 58, 137, 77, 185, 65, 78, 71, 35, 155, 176, 109, 195, 111, 161, 232, 195, 226, 88, 134, 73, 60, 11, 215, 63, 219, 88, 38, 2, 175, 14, 213, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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