Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b162ec0f78c84e4e89966ab84f08d68319ad400df2f49430a0aba93e4e55693

Tx prefix hash: 7460aed4ca293f780e27285bc81886735ecbcea0bb0fdb04f7ca5a6d26d40de7
Tx public key: 779f062db31b8e4e78525f0035dca4419e62a4ce5dfab80b771c03e2590a8954
Timestamp: 1723758007 Timestamp [UCT]: 2024-08-15 21:40:07 Age [y:d:h:m:s]: 01:147:16:38:55
Block: 1088712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364101 RingCT/type: yes/0
Extra: 01779f062db31b8e4e78525f0035dca4419e62a4ce5dfab80b771c03e2590a8954021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f022b87d6a2546ca465c4dc9a58a149f04b7b2635ece730e9a4191b37c8674e 0.600000000000 1563329 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": 1088722, "vin": [ { "gen": { "height": 1088712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f022b87d6a2546ca465c4dc9a58a149f04b7b2635ece730e9a4191b37c8674e" } } ], "extra": [ 1, 119, 159, 6, 45, 179, 27, 142, 78, 120, 82, 95, 0, 53, 220, 164, 65, 158, 98, 164, 206, 93, 250, 184, 11, 119, 28, 3, 226, 89, 10, 137, 84, 2, 17, 0, 0, 0, 3, 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