Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b4b7a2625626b6996ed345f1593e4a21070639984b421e3e8164a03c0f079cc

Tx prefix hash: 73912faf583bad9fac27f5275c74cca71eacc95ad4bf10733bde22d72a6ea7c5
Tx public key: 533aa5dc8417d08eef8e0392a4484a1923489b40b1bddd456c37e9256543d5f4
Timestamp: 1737962606 Timestamp [UCT]: 2025-01-27 07:23:26 Age [y:d:h:m:s]: 00:141:17:46:26
Block: 1206093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101222 RingCT/type: yes/0
Extra: 01533aa5dc8417d08eef8e0392a4484a1923489b40b1bddd456c37e9256543d5f40211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0c90f701a7c12cdaa8e44f9de156c1dd51031e23b930e7ab4825602b08a9c6b 0.600000000000 1692794 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": 1206103, "vin": [ { "gen": { "height": 1206093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0c90f701a7c12cdaa8e44f9de156c1dd51031e23b930e7ab4825602b08a9c6b" } } ], "extra": [ 1, 83, 58, 165, 220, 132, 23, 208, 142, 239, 142, 3, 146, 164, 72, 74, 25, 35, 72, 155, 64, 177, 189, 221, 69, 108, 55, 233, 37, 101, 67, 213, 244, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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