Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04abfe79e90463799e72768761e1660ddc0682953b42f2b456ba56a523164205

Tx prefix hash: 370806b34d4a9021e8eefc6a2665d33084eb166cabe8eff3d4f56f8702076074
Tx public key: 0dd041c8b56a8984f223206a4f22e9c58e229a2c3418e4306eb07edb7aa66573
Timestamp: 1583238005 Timestamp [UCT]: 2020-03-03 12:20:05 Age [y:d:h:m:s]: 04:299:20:31:55
Block: 75555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1108629 RingCT/type: yes/0
Extra: 010dd041c8b56a8984f223206a4f22e9c58e229a2c3418e4306eb07edb7aa6657302110000005703d36d11000000000000000000

1 output(s) for total of 344.870238267000 dcy

stealth address amount amount idx
00: 59b697fa49208d8aa15b88b1761afd71e1250561f6dac494287b70ea7e5ab7a4 344.870238267000 139507 of 0

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": 75565, "vin": [ { "gen": { "height": 75555 } } ], "vout": [ { "amount": 344870238267, "target": { "key": "59b697fa49208d8aa15b88b1761afd71e1250561f6dac494287b70ea7e5ab7a4" } } ], "extra": [ 1, 13, 208, 65, 200, 181, 106, 137, 132, 242, 35, 32, 106, 79, 34, 233, 197, 142, 34, 154, 44, 52, 24, 228, 48, 110, 176, 126, 219, 122, 166, 101, 115, 2, 17, 0, 0, 0, 87, 3, 211, 109, 17, 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