Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2664dd05b228eac95c299421be61480b8314cc866f6691435126c0fcfacbfc02

Tx prefix hash: 01e2cb479a1654d518b10b94d07dbe09e40b556f17ad22269ee68785f8c7960d
Tx public key: eda9c43f614e710f4a67f08ac5fe5b1e81a58099b8df8c0e3db01970108e04d5
Timestamp: 1722917729 Timestamp [UCT]: 2024-08-06 04:15:29 Age [y:d:h:m:s]: 00:169:18:47:06
Block: 1081741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121424 RingCT/type: yes/0
Extra: 01eda9c43f614e710f4a67f08ac5fe5b1e81a58099b8df8c0e3db01970108e04d5021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd416dadf772b489bc2f0a69a92f9be4c9d40ee5ec35bd62a60463dea5796a3c 0.600000000000 1555562 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": 1081751, "vin": [ { "gen": { "height": 1081741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd416dadf772b489bc2f0a69a92f9be4c9d40ee5ec35bd62a60463dea5796a3c" } } ], "extra": [ 1, 237, 169, 196, 63, 97, 78, 113, 15, 74, 103, 240, 138, 197, 254, 91, 30, 129, 165, 128, 153, 184, 223, 140, 14, 61, 176, 25, 112, 16, 142, 4, 213, 2, 17, 0, 0, 0, 9, 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